Skip to main content
Historic England

Conservation area

There is a problem

  • start-date column must be in YYYY-MM-DD format

Hoddlesden

reference
3069
name
Hoddlesden
designation-date
document-url
documentation-url
https://www.blackburn.gov.uk/land-and-property/conservation-areas
geometry
MULTIPOLYGON (((-2.433482 53.694892,-2.433206 53.694830,-2.432795 53.694720,-2.432751 53.694700,-2.432489 53.694523,-2.432420 53.694572,-2.432026 53.695132,-2.431994 53.695140,-2.431965 53.695136,-2.431763 53.695054,-2.431701 53.695045,-2.431618 53.695071,-2.431207 53.695374,-2.431132 53.695415,-2.431107 53.695365,-2.430406 53.695004,-2.430204 53.695160,-2.430142 53.695191,-2.430788 53.695543,-2.430570 53.695686,-2.430664 53.695778,-2.430528 53.695832,-2.430543 53.695847,-2.430404 53.695901,-2.430595 53.696078,-2.430614 53.696147,-2.430368 53.696165,-2.429922 53.696150,-2.429737 53.696152,-2.429885 53.696281,-2.429905 53.696311,-2.429911 53.696337,-2.429902 53.696365,-2.429793 53.696477,-2.429779 53.696499,-2.429777 53.696518,-2.429943 53.696601,-2.430252 53.696734,-2.430395 53.696768,-2.431917 53.696576,-2.431883 53.696873,-2.432225 53.696871,-2.432263 53.696534,-2.432347 53.695970,-2.432925 53.695978,-2.432922 53.695697,-2.433482 53.694892)))
point
POINT (-2.431659 53.695786)
notes
No Appraisal document.
organisation
entry-date
2025-04-01
start-date

start-date must be a real date

end-date

How to fix this issue

Your dataset is missing the start-date column.

The Conservation area guidance explains how to fix the issue:

start-date

The date the validity of the record starts, written in YYYY-MM-DD format. Usually, this will be the same as the designation date. If anything about the conservation area has changed, for example, the boundary, it should be the date of that change.

Example:

1984-04-25

With dates, some data is better than no data, so:

  • 1984 is fine
  • 1984-04 is better
  • 1984-04-25 is brilliant

How to improve Historic England’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL